The following defects are open in this release of the software.
Parent Defect ID: | NPB-5182 | Issue ID: | NPB-5182 |
Severity: | S2 - Major | ||
Product: | NPB | Reported in Release: | NPB 21.1.1.0 |
Symptom: | Entity MIB item entPhysicalVendorType does not return any Vendor type OIDs, instead it just returns {0 0} when SNMP walk is performed | ||
Condition: | This happens during SNMP walk of entPhysicalVendorType in the entity MIB. | ||
Workaround: | No workaround | ||
Recovery: | No recovery available |
Parent Defect ID: | NPB-5188 | Issue ID: | NPB-5188 |
Severity: | S3 - Moderate | ||
Product: | NPB | Reported in Release: | NPB 21.1.1.0 |
Symptom: | "Link Fault Status" field in "Show interface ethernet" might show incorrect fault status. | ||
Condition: | "no shutdown" on the ethernet interface. | ||
Recovery: | No functional impact. |
Parent Defect ID: | NPB-5724 | Issue ID: | NPB-5724 |
Severity: | S3 - Moderate | ||
Product: | NPB | Reported in Release: | NPB 21.1.2.0 |
Symptom: | LACP port-channel remains down after replaying the configuration with LACP rate as 'fast' in the member interfaces. | ||
Condition: | The issue is seen when the LACP configurations are replayed with the node in default-configs. only when "lacp rate fast" is configured on member ports. | ||
Workaround: | If we reboot the system with config, it will work properly or change the "lacp rate normal", and after the port-channel comes up again, change it to "lacp rate fast" on member ports. | ||
Recovery: | Disable & enable lacp in the global config mode. ('no protocol lacp' & 'protocol lacp') |
Parent Defect ID: | NPB-6285 | Issue ID: | NPB-6285 |
Severity: | S3 - Moderate | ||
Product: | NPB | Reported in Release: | NPB 21.2.2.0 |
Symptom: | The 100G-DR, FR is a single laser. On the optical side it runs PAM4 at 53.125 Gb. PAM4 is 2 bits per symbol which gives you 100G. Channels 2,3 and 4 should be quiet. Hence tx, rx, txbias data shows proper for channel-1, inf or 0.00 on channel-2,3,4 |
Parent Defect ID: | NPB-6302 | Issue ID: | NPB-6302 |
Severity: | S3 - Moderate | ||
Product: | NPB | Reported in Release: | NPB 21.2.1.0 |
Symptom: | Help string has to be updated to display the range from 1-4095. Documentation has been updated. | ||
Condition: | While configuring the ACL rules, the help string shows the priority range as 1-65535. | ||
Workaround: | Configure the rules with priority ranging from 1 to 4095. | ||
Recovery: | Configure the rules with priority ranging from 1 to 4095. |
Parent Defect ID: | NPB-6311 | Issue ID: | NPB-6311 |
Severity: | S3 - Moderate | ||
Product: | NPB | Reported in Release: | NPB 21.1.2.5 |
Symptom: | "show grpc-server gnmi statistics" command output does not indicate external IP address which originated the gnmi subscription request. | ||
Condition: | "show grpc-server gnmi statistics" command output always indicates internal IP address as the originator of GNMI subscriptions |
Parent Defect ID: | NPB-6313 | Issue ID: | NPB-6313 |
Severity: | S3 - Moderate | ||
Product: | NPB | Reported in Release: | NPB 21.2.2.0 |
Symptom: | For single lane optics, currently the 'show cli' command displays the media information for all the lanes. | ||
Condition: | This is applicable for single lane optics like FR and DR. | ||
Workaround: | Only the first lane data to be considered for single lane optics. | ||
Recovery: | None |
Parent Defect ID: | NPB-6315 | Issue ID: | NPB-6315 |
Severity: | S3 - Moderate | ||
Product: | NPB | Reported in Release: | NPB 21.1.2.7 |
Symptom: | All line cards of NPB restarted randomly. | ||
Condition: | Issue happened with NPB box powered using DC PSU and there is voltage fluctuation causing all LCs to go down. | ||
Workaround: | Use 'system slot on' command to bring up the LC, if LCs are in Present state. | ||
Recovery: | All LCs recover when voltage is normal. |
Parent Defect ID: | NPB-6318 | Issue ID: | NPB-6318 |
Severity: | S3 - Moderate | ||
Product: | NPB | Reported in Release: | NPB 21.1.2.7 |
Symptom: | Traffic is not getting forwarded out of few egress ports. | ||
Condition: | Traffic is not getting forwarded out of few egress ports. | ||
Workaround: | With rebooting the system, the condition is getting cleared and traffic forwarded. | ||
Recovery: | With rebooting the system, the condition is getting cleared and traffic forwarded. |